Software Engineering

R. Ravichandran ¹, M. Punithavalli ², V. Vijayalakshmi

Affiliations
1 PSG College of Technology, IN
2 Computer Applications Department, Sri Ramakrishna College of Engineering, Coimbatore, IN

Abstract

This study probed into improving the process capability in defined level software companies to achieve high process maturity with respect to effort deviation and schedule deviation using Statistical Process Control (SPC) technique. Using the results of research through literature review, collection of data from software industry this study would be identified the relative importance of SPC, software quality and software process. SPC can be applied in defined level companies to improve the process maturity [1]. A case study is conducted in the present study to obtain practical evidence on the validity of the reasoning about statistical process control in achieving high level process maturity at defined level companies. The real time data were collected for effort deviation and schedule deviation for the different phases of the project life cycle considering two different languages namely VB.NET and ASP.NET. Projects were grouped language wise for analysis and the control limits were constructed and defined for effort deviation and schedule deviation separately. The applicability of SPC through control charts in improving the process capability with respect to effort deviation and schedule deviation have been validated considering projects done in two different languages.

Keywords

Statistical Process Control (SPC), Effort Deviation, Schedule Deviation, Process Maturity.

Full Text

     

S. Preetha ¹, M. Punithavalli ¹

Affiliations
1 Sri Ramakrishna College of Arts and Science for Women, Coimbatore, IN

Abstract

Software testing is an important but expensive process because about fifty percent of the total development cost is spent for it. However, this part is the first one to miss by software developers if there is a limited time to complete the project. Tests are commonly generated from program source code, graphical models of software (such as control flow graphs), and specifications/requirements. Creating test cases manually is a huge work for software developers. It is time consuming and error prone. A solution which automatically generates test cases and test data can help the software developers to create test cases from software designs/models in early stage of the software development (before coding). High quality software cannot be done without high quality testing. Heuristic techniques can be applied for creating quality test data. A fault is defined as a textual problem with the code resulting from a mental mistake by the programmer or designer. A fault is also called a defect. Fault-based testing refers to the collection of information on whether classes of software faults (or defects) exist in a program. Since testing can only prove the existence of errors and not their absence, this testing approach is a very sound one. In this paper we describe the methods for evaluating the fault, methods for characterizing faults.

Keywords

Software Testing, Fault, Test Cases.

Full Text

     

R. V. Siva Balan ¹, M. Punithavalli ²

Affiliations
1 Department of Computer Science and Information Technology Sri Krishna Arts and Science College, Coimbatore, IN
2 Department of Computer Applications, Sri Ramakrishna College of Arts and Science for Women, Coimbatore, IN

Abstract

The UML extension is based on design principles that are derived from characteristics of MAS (Multi-Agent Systems) and concept of software architecture which helps to design reusable and well structured multi-agent architecture. The extension allows one to use original object oriented method without syntactic or semantic changes which implies the preservation of OO productivity, i.e., the availability of developers and tools, the utilization of past experiences and knowledge, and the seamless integration with other systems. This survey discusses in more detail how architectures can be described and the uses of such descriptions. Much research so far has also been dedicated to methods and case studies, to make the research of practical interest. This survey describes how the quality of the software can be ensured to a certain degree through informal approaches - not least because an architectural description provides a common understanding around which different stakeholders can meet and discuss a system. Formal approaches are also emerging, and there are a number of formal languages for description of a system's software architecture.

Full Text

     

R. Ravichandran ¹, M. Punithavalli ²

Affiliations
1 KGiSL Educational Institutions, Coimbatore, IN
2 Department of Computer Science, Sri Ramakrishna College of Arts and Science for Women, Coimbatore, IN

Abstract

As organizations implement systematic software reuse programs to improve productivity and quality, they must be able to measure their progress and identify the most effective reuse strategies. This is done with reuse metrics and models. Reusability of interfaces has now become more generalized approach for application development. The main advantages of this are reduced development time, cost and efforts along with several others. These advantages are mainly contributed by the reuse of already built-in software components. In order to realize the reuse of components effectively in interfaces, it is required to measure the reusability of components. Paper proposes several reusability metrics in terms of cost and productivity like Reuse cost avoidance, Reuse value added and Additional development cost, which can be used significantly for business applications. Component-based software development relies on reusable components in order to improve quality and flexibility of products as well as increasing development productivity. This paradigm promotes deployment of reusable components as black-box units that can only work and communicate with one another through their well defined interfaces. In this paper, understandability of component interfaces is considered as a major quality affecting reusability of software components. A set of metrics for measuring properties believed to be relevant to understandability and reusability of software components are presented. Then, their usefulness and relevance are analyzed based upon data gathered from the measurement of a variety of component interfaces. The paper concludes with some ideas for further research in this area.

Keywords

CBSD, Interface, Metrics, Reuse, Inheritance.

Full Text